[ Top | Up |
Prev | Next |
Map | Index ]
Analog's reports
This section summarises all of analog's reports, and the main commands which
control them. For details on these commands, see the sections on
Time reports,
Other reports and
Hierarchical reports.
For exact details on what is counted in each report, see the section on
Analog's definitions.
Program started at Thu-24-Sep-1998 13:48.
Analysed requests from Wed-16-Sep-1998 09:52 to Mon-21-Sep-1998
02:04 (4.7 days).
The top two lines of the report tell you when the program was run, and
which dates it includes data from.
(Figures in parentheses refer to the 7 days to 24-Sep-1998 13:48).
Successful requests: 79,646 (48,947)
Average successful requests per day: 17,036 (6,992)
Successful requests for pages: 31,138 (18,689)
Average successful requests for pages per day: 6,660 (2,669)
Failed requests: 9,008 (6,378)
Redirected requests: 344 (235)
Distinct files requested: 8,180 (2,884)
Distinct hosts served: 6,640 (4,991)
Corrupt logfile lines: 2
Data transferred: 976,921 kbytes (627,067 kbytes)
Average data transferred per day: 208,967 kbytes (89,581 kbytes)
The General Summary contains some overall statistics about the data being
analysed. For what the various lines mean, see the section on
Analog's definitions.
The figures in parentheses represent the seven days given at the top of this
report: it's the seven days before the TO time if there was a
TO command, or if not the seven days before the report was run.
You can turn this report on or off with the
GENERAL command. You can include
or exclude the figures for the last seven days with the
LASTSEVEN command.
You may get slightly different lines to those above, depending on other
options you have set.
Each unit () represents 800 requests for pages, or part thereof.
week beg.: #reqs: pages:
---------: -----: -----:
13/Sep/98: 69614: 25277:
20/Sep/98: 10032: 5861:
Busiest week: week beginning 13/Sep/98 (26,654 requests for pages).
These reports tell you how many requests there were in each time
period. They also tell you which was the busiest time period.
You can control whether each report is included or not with the appropriate
ON or OFF command.
You can control which columns are listed by the
COLS commands. You can control
which measurement to use for the bar charts and the "busiest" line
by the GRAPH commands. You can
determine how many rows are displayed with the
ROWS commands. You can display the
lines backwards or forwards in time by the
BACK commands. You can change the
graphic used for the bar charts with the
BARSTYLE command.
Each unit () represents 150 requests for pages, or part thereof.
day: #reqs: pages:
---: -----: -----:
Sun: 2031: 1193:
Mon: 8001: 4668:
Tue: 0: 0:
Wed: 13934: 5915:
[etc.]
These reports tell you the total number of requests in each day of the week,
or each hour of the day, over the time period given at the very top of the
report. (It's not the average, nor is it the figures for just the last week or
last day).
You can control whether each report is included or not with the appropriate
ON or OFF command.
You can control which columns are listed by the
COLS commands. You can control
which measurement to use for the bar charts by the
GRAPH commands. You can change the
graphic used for the bar charts with the
BARSTYLE command.
Listing the first 5 files by the number of requests, sorted by
the number of requests.
#reqs: %bytes: last date: file
-----: ------: ---------------: ----
4123: 2.29%: 21/Sep/98 01:57: /~sret1/analog/
3064: 0.15%: 21/Sep/98 01:54: /~sret1/analog/analogo.gif
1737: 0.01%: 21/Sep/98 01:53: /~sret1/images/bar1.gif
1692: 0.01%: 21/Sep/98 01:53: /~sret1/images/bar16.gif
1685: 0.01%: 21/Sep/98 01:53: /~sret1/images/bar8.gif
67345: 97.54%: 21/Sep/98 02:04: [not listed: 8,175 files]
The rest of the reports are all quite similar. Here is a list of them. If
you're unfamiliar with some of the terms, see the section on
Analog's definitions.
- The Host Report lists all computers which downloaded files from you.
- The Domain Report lists which countries those computers came
from. (If you only get "unresolved numerical addresses", see the
FAQ.)
- The Request Report (the example above) lists which files were
downloaded.
- The Directory Report lists which directories those files came from.
- The File Type Report lists the file types (actually, extensions) of
those files.
- The File Size Report breaks them down by size.
- The Redirection Report lists the filenames which resulted in redirections.
- The Failure Report lists the filenames which caused errors.
- The Referrer Report lists which pages linked to your files.
- The Referring Site Report lists the servers those referrers were on.
- The Redirected Referrer Report lists the referrers which led to
redirections.
- The Failed Referrer Report is essentially a broken link report.
- The Browser Report lists the detailed versions of browsers used,
and the Browser Summary collects them by vendor.
- The Virtual Host Report and the User Report are obvious.
- The Failed User Report lists the users who caused errors.
- The Status Code Report lists the number of each
HTTP status code that you had.
Whether you can get all of these reports depends on what information is
recorded in your logfile.
As usual, you can control whether each report is included or not with the
appropriate ON or OFF
command. You can control which columns are listed by the
COLS commands. You can change
how the reports are sorted by the
SORTBY commands. You can control
how many items are listed by the
FLOOR commands. You can include or
exclude individual items with the output
INCLUDE and EXCLUDE commands. You can change the
names of items in the reports with the
OUTPUTALIAS commands.
The "not listed" line at the bottom counts those items which
didn't get enough traffic to get above the FLOOR for the report,
and those which were explicitly EXCLUDEd.
Most of these reports have a hierarchical structure, like this example for
the Domain Report:
Listing the first 5 domains by the number of requests, sorted by
the number of requests.
#reqs: %bytes: domain
-----: ------: ------
13243: 16.23%: .com (Commercial)
1262: 1.26%: aol.com
11783: 25.64%: .jp (Japan)
9592: 22.19%: ad.jp
1043: 1.97%: co.jp
10073: 11.62%: .net (Network)
1926: 1.71%: uu.net
9657: 13.31%: [unresolved numerical addresses]
7388: 8.04%: .uk (United Kingdom)
5792: 5.74%: ac.uk
1510: 1.99%: co.uk
18502: 25.16%: [not listed: 82 domains]
You can control which items are listed on the lower levels by the
SUB family of commands (the report
INCLUDEs and EXCLUDEs only work at the top level).
There are also separate
sub-SORTBY and
sub-FLOOR commands for the
lower levels. (Called
ARGSSORTBY and
ARGSFLOOR for some reports,
such as the Request Report.)
Notice that the lower levels are always listed with their parents, so they
break up the sort order. Also, they don't count towards the total number of
items listed (so there are only 5 domains listed in the example above).
Which files are linked to in the Request Report is controlled by the
LINKINCLUDE and
LINKEXCLUDE commands, and which files are linked to in the
various referrer reports is controlled by the
REFLINKINCLUDE and
REFLINKEXCLUDE commands. The links in the Request Report are
also affected by the BASEURL
command.
This analysis was produced by analog3.32/Unix.
Running time: 8 seconds.
At the end of the report you can see which version of analog produced the
report, and how long the report took to run.
Stephen Turner
Personal e-mail: analog-author@lists.isite.net
Need help with analog? Subscribe to the analog-help
mailing list
[ Top | Up |
Prev | Next |
Map | Index ]